This PR also applies the program_suffix to phar.phar such that a suffix of 7.4 results in phar.phar7.4. This is similar to the way that I've seen deb/apt-based distros package phar but is odd in that it does confuse the meaning of the .phar file extension.

An alternative would be to apply the program_suffix such that the resultant filename of phar.phar is phar7.4.phar, preserving the .phar file extension, instead of phar.phar7.4

This PR also applies the program_suffix to phar.phar such that a suffix of 7.4 results in phar.phar7.4. This is similar to the way that I've seen deb/apt-based distros package phar but is odd in that it does confuse the meaning of the .phar file extension.

An alternative would be to apply the program_suffix such that the resultant filename of phar.phar is phar7.4.phar, preserving the .phar file extension, instead of phar.phar7.4

I think your alternative suggestion makes more sense, it should be phar7.4.phar. I wonder if you also need to add the suffix to the man page files?

Also cc @remicollet, I'm not sure what assumptions are in place here.

@nikic I've implemented phar$(program_suffix).phar. You're right about the man page files. I've now added the suffix to the phar man page files

--program-prefix and --program-suffix are now both applied to phar and phar.phar and their man page paths in essentially the same way that they are for php, phpdbg, php-config, and phpize binaries